home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 25
/
Cream of the Crop 25.iso
/
os2
/
vac23.zip
/
HISTORY.DOC
< prev
next >
Wrap
Text File
|
1997-04-03
|
31KB
|
769 lines
AdeptXbbs What's new/changed/fixed from Version 1/07f. (1.07f Was the last
official release from AdeptSoft).
- Since 107f was released, the menu system has been completely changed.
Adept now compiles menus into *.menu.bin files, it automatically
detects any changes you have made to the *.menu ascii files and
recompiles it (on the fly) into the .bin file. This new menuengine
is 100% faster than the old ascii menuengine, and supports options
not avalable in the old menu engine. Listed Below is the documentation
for the new menu structure. you put these keywords into a .menu ascii
file. Example Main.Menu and when adept compiles it you will have
Main.menu and Main.Menu.Bin. If u ever want to make changes, simply
edit the Main.Menu file and adept will recompile it on the fly.
New Menu File Format:
******************************************************************************
The KeyWords below are currently recognized by the tower menu engine used
in the Hagar builds. These keywords should be put into xxxx.Menu files
The engine will scan the .Menu files and produce xxxx.Menu.Bin for it's own
use, the bin files are not readable via editors or such like. If a change is
made to a .Menu file the corresponding .Menu.Bin file will be recompiled on
the fly the very next time that menu is chosen. Note that if u are logged into
a menu and make a change to the .Menu file it will not take effect till u exit
that menu and reenter it. (Natch, the system has to recompile the bin file
and doesn't know its been changed yet :>)
*******************************************************************************
The users current location should now be properly displayed. Also check
out the 'NEWLOCATION' keyword for menu items. :)
The following Menu Functions are available.
BEGINMENU - Mark the begining of a menu.
ENDMENU - Mark the end of the a menu.
Everything before and after the above are ignored by the menu parser.
PROMPT - Menu Prompt Text
PROMPTCOLOR - Menu Prompt Color
DISPLAYFILE - File to display to users instead of menu item text
MENULOCATION - Currently location on the BBS
MENUFLAGS - Menu option flags.
The above options can be anywhere within the BEGINMENU and ENDMENU
options, but are preferably at the top of the menu to assist in
readability.
BEGINMENUITEM - Begin Item Definition
ENDMENUITEM - End Item Definition
All of the below functions are ONLY available within the menu item
definition. All of the below are relayed to the 'KEY' keyword. The
'KEY' keyword contains the key that represents the menu item.
KEY - Key to assign to the menu item.
MENUCOMMAND - Command to execute when the 'KEY' is pressed.
DISPLAYSTRING - String to display to user when displaying the menu items
along with or without a Display File.
DISPLAYCOLOR - Initial color for the display string
DATAOPTION - Optional data for the menu command
MINAGE - Minimum age allowed to use this command
MAXAGE - Maximum age allowed to use this command
MINSEC1 - Minmum security level (based on users security #1) to use
command
MAXSEC1 - Miximum security level (based on users security #1) to use
command
MINSEC2 - Minmum security level (based on users security #2) to use
command
MAXSEC2 - Miximum security level (based on users security #2) to use
command
FLAGS1 - User flag comparison for access to this command flags #1
FLAGS2 - User flag comparison for access to this command flags #1
GENDER - Genders (YES, Genders I.E. MFO (Male, Female, Other or
whateever you have defined in the language.text as possible
genders)) allowed to access this command.
STARTTIME - Start time that this command becomes available. (24hr)
ENDTIME - Ending time that this command becomes unavailable. (24hr)
MINONLINETIME - Minimum time user is online before they can use this
command.
MAXONLINETIME - Maximum time a user can be online before command becomes
unavailable.
MINCALLS - Minimum calls that the user has made to the BBS before
command becomes available.
MAXCALLS - Maximum calls that the user has made to the BBS before
command becomes unavailable.
MINPOSTS - Minimum number of messages posted before user can access
this command.
MAXPOSTS - Maximum number of messages posted before command becomes
unavailable.
MINUPLOADS - Minimum number of uploads needed to access this command.
MAXUPLOADS - Maximum number of uploads before command becomes unavailable.
MINDOWNLOADS - Minimum number of download needed to access this command.
MAXDOWNLOADS - Maximum number of downloads before command becomes
unavailable.
GROUP - Group number that the user needs to belong to to access
command.
PORTFLAGS - Type of port needed (TCP, Comm, Pipe) to access command.
NEWLOCATION - Location to set when user executes this command for
calls to items/functions that do not set the system
location.
All of the above may exist within a BEGINMENUINITEM/ENDMENUITEM in any
particular order.
Included here is a sample menu that run on my system, it is the newuser.menu
that is autoexecuted any time a new user logs on. *ALL* adept systems *NEED*
a Newuser.Menu or New users will simply get default user settings. NewUser.Menu
is executed if it exists int he \adept\menus directory, anytime a user name
is not found in the userbase.
Sample NewUser.Menu:
BEGINMENU
PROMPTCOLOR 0
MENULOCATION Newuser Logon
MENUFLAGS 0
BEGINMENUITEM
KEY 1
MENUCOMMAND 144
DISPLAYSTRING ANSI Color
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY 2
MENUCOMMAND 132
DISPLAYSTRING High Ascii
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY 3
MENUCOMMAND 135
DISPLAYSTRING More Prompts
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY 4
MENUCOMMAND 157
DISPLAYSTRING Clear Screen
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY 5
MENUCOMMAND 133
DISPLAYSTRING Cold Input
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY 6
MENUCOMMAND 138
DISPLAYSTRING Width of screen
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY 7
MENUCOMMAND 134
DISPLAYSTRING Length of screen
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY 8
MENUCOMMAND 154
DISPLAYSTRING Full screen editor
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY 9
MENUCOMMAND 165
DISPLAYSTRING View Mail Processing
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY T
MENUCOMMAND 51
DISPLAYCOLOR 0
DATAOPTION Phone.Asc
ENDMENUITEM
; BEGINMENUITEM
; KEY 0
; MENUCOMMAND 139
; DISPLAYSTRING Change Phone
; DISPLAYCOLOR 0
; ENDMENUITEM
BEGINMENUITEM
KEY 0
MENUCOMMAND 10
DISPLAYSTRING Change Address
DISPLAYCOLOR 0
DATAOPTION phone.cmd
ENDMENUITEM
BEGINMENUITEM
KEY A
MENUCOMMAND 130
DISPLAYSTRING Change Address
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY 9
MENUCOMMAND 51
DISPLAYCOLOR 0
DATAOPTION getpassword1.asc
ENDMENUITEM
BEGINMENUITEM
KEY B
MENUCOMMAND 137
DISPLAYSTRING Change Password
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY C
MENUCOMMAND 159
DISPLAYSTRING Change Gender
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY D
MENUCOMMAND 156
DISPLAYSTRING Birthday
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY E
MENUCOMMAND 155
DISPLAYSTRING MailType
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY F
MENUCOMMAND 146
DISPLAYSTRING File Transfer Protocol
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY G
MENUCOMMAND 166
DISPLAYSTRING Change Archiver
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY H
MENUCOMMAND 158
DISPLAYSTRING Cpu type
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY I
MENUCOMMAND 136
DISPLAYSTRING Handle
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY J
MENUCOMMAND 140
DISPLAYSTRING Interests
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY S
MENUCOMMAND 51
DISPLAYCOLOR 0
DATAOPTION Show.Asc
ENDMENUITEM
BEGINMENUITEM
KEY K
MENUCOMMAND 141
DISPLAYSTRING Change Info Shown
DISPLAYCOLOR 0
ENDMENUITEM
BEGINMENUITEM
KEY Z
MENUCOMMAND 10
DISPLAYCOLOR 0
DATAOPTION maiden.srx
ENDMENUITEM
BEGINMENUITEM
KEY K
MENUCOMMAND 51
DISPLAYCOLOR 0
DATAOPTION policy.asc;7
ENDMENUITEM
BEGINMENUITEM
KEY T
MENUCOMMAND 51
DISPLAYCOLOR 0
DATAOPTION super1.asc;7
ENDMENUITEM
BEGINMENUITEM
KEY R
MENUCOMMAND 51
DISPLAYCOLOR 0
DATAOPTION Trial.asc;7
ENDMENUITEM
BEGINMENUITEM
KEY Y
MENUCOMMAND 10
DISPLAYSTRING AutoVerify Telnet users
DISPLAYCOLOR 0
DATAOPTION autoupgrade.srx
ENDMENUITEM
ENDMENU
The above is the layout of the new menustructure, simply make your 107f menus
conform to this structure and you will be away.
Note: to make the transition from 107f to this version, there is a MenuCvt.Cmd
rexx script included in the zip file, simply place it in your \adept\menus
dir and execute it. It will convert your existing 107f menus to the new format.
The 107f menus will be saved in *.menu.old files, in case you need them to
refer to at anytime. You should manually check the converted menus, since
menucvt.cmd is not very intelligent. it tries to convert your menus, but it
is possible it may run across something it can't handle, so *CHECK* your new
menus before firing up adept to make sure they are all right.
****************************************************************************
There is now a new chatserver for Adeptxbbs, the 107f chatserver.exe
should no longer be used, instead run the new Cserver.Exe that is included
in the zip file. This new Chatserver relies on IBM's Tcpip loopback being setup
correctly. Follow the nstructions below to see if you have your loopback
properly configured, and how to configure it if u don't.
This chat server uses IBM's TCPIP as it's connection
medium, If your local loopback is setup wrong it will not work.
If you do not see the following when you type ifconfig lo on your command
line, your loopback is not setup correctly.
[C:\]ifconfig lo
lo: flags=809<UP,LOOPBACK>
inet 127.0.0.1 netmask ffffff00x
If you are running warp connect you can add the line
ifconfig lo 127.0.0.1 to your \mptn\bin\setup.cmd
if you are running other versions of OS/2 you can
add 'ifconfig lo 127.0.0.1' to your startup.cmd.
The server has no limit to the number of users.
Note: That if your loopback is not setup adept will "hang" for several
minutes during the login sequence for a remote or even local logon.
Run Cserver.Exe from a seperate session, I recommend using a looping
cmd file in case it goes down for some reason. The looping cmd file will
restart it. Here is my cmd file that I use on my system.
:top
cserver
wait :0:0:5
goto top
Wait is simply a little util that waits the specified time (in this case
5 seconds) then exits. this little loop will ensure your chat functions
will always be avilable.
***************************************************************************
Added a new menu type, 1002. Logoff and Relog on.
This will display prompt #935 (currently unused) and display the
file Relogin.Asc/Ans/Avt to the user before commencing with the
relogin. This is a COMPLETE logoff with relogin, except that it
doesn't drop carrier. ATEND.CMD will be run, etc. I have added
two new rexx function functions.
AdeptSetRelogin(line, TRUE/FALSE) - Tells the BBS to relog the user back
on after logoff is completed.
AdeptCheckForRelogin(line) - Will return 1 if the user is requesting a
relogin after logoff.
{PQ - Displays press any key to continue if the displayed amount of lines
is more then the users screen length.
Added a new line to language.text, item #435, User currently not
available for chat. I.E. Writing a message or marked as busy.
****************************************************************************
New Rexx Functions for the new Chatserver:
The AdeptInitRexx(line) command is REQUIRED in order to use the
following functions.
Constants such as the IRC_NOTIMELEFT are defined via this command so
if you don't use it you won't be able to use the system constants.
The IRC in the IRC_ constants stand for Input Return Code, NOT Internet
Relay Chat.
Added a new rexx function AdeptSysChatMsg(line, Text)
You format how the text is to be displayed to the remote user. Please
use the {COLOR metas or ascii users will get ansi if you put it in the
Text.
This can be used for annoucements such as User so and so has logged on
via node such and such. Be creative.
RetC = AdeptSysChatInput(line, "BUFFERNAME")
The above function will return 1 if all is well and the user pressed
return. It can also return any of the below constants.
A function very similiar to AdeptInput except specificly designed to
be used with multi-node chat.
The IRC constants are:
LOSTCARRIER if the carrier had been dropped.
IRC_NOTIMELEFT if no time is remaining.
IRC_LOCKEDOUT if the sysop locked the user out.
IRC_MORON if the system hit the moron key.
IRC_REPROMPT to request a redraw of the prompt or screen.
IRC_ENDSYSOPCHAT if the sysop broke into chat and just ended it.
IRC_IDLETIMEOUT if the user idle's out
IRC_CHATWAITING if a chat message is waiting to be processed.
IRC_CHATDOWN if the chat server went down.
"Buffer" would be the variable name to place what the user typed on the
input line.
RetC = AdeptSysChatGetMsg(line)
Ok, this command was extreanly complex, so I decided to symplify it as
best as possible.
You call this when you receive a IRC_CHATWAITING.
It will Return
0 - Didn't receive a packet or bad packet
1 - Received a chat packet that doesn't have a chatmsg attached
2 - Received a chat packet that does have a chatmsg attached
3 - Received a chat packet that does have a chatmsg with a chat data
packet attached.
Instead of having you pass a bazillion variables I automatically stuff
the variables for you with the data and known names.
The variables are
The following are set if the return code is 1
PKTTYPE - Packet type definitions follow.
100 - Standard Public Conference Message
101 - No Prepended Public Conference Message
102 - Private message to anouther user/node
103 - Invite a user to a channel
104 - Leave chat
105 - System Global Message to all no matter where
PKTSERIAL - Packet Serial Number (Currently the time it was sent)
PKTCRC - 32 bit CRC of the ChatMsg if one it to be sent for
validation of the chat message.
The following are also set if the return code is 2
CHATMSGFROM - User or Node number the chat message was from.
CHATMSGFLAGS - Flags for the message (Currently unused)
CHATMSGSCRAMBLE - Scramble code for the message, I.E. Only those with the
same code set can see it.
CHATMSGTO - Who the message is to. If blank, it's considered to be
a public style message for use public chat.
The following are also set if the return code is 3
CHATMSGDATALEN - Length of the data.
CHATMSGDATACRC - CRC of the Data.
CHATMSGDATA - The data, usually the chat messages text, could be
binary if you so desire. 4k limit.
RetC = AdeptSysChatJoinConf(line, ConferenceName)
0 = Join Not Successful
1 = Access Denied to Channel
2 = Channel Joined
RetC = AdeptSysChatLeaveConf(line)
Returns 1 every time.
If the user is in Conference name it will remove the user from the
conference.
RetC = AdeptSysChatPubMsg(line, Message Text)
0 = Message wasn't sucessfully sent misc error
1 = Message was sent
The user must be a in a conference for others to see the message
or it will just go into limbo.
RetC = AdeptSysChatPrivMsg(line, Node, Message Text)
0 = Message wasn't sucessfully sent mirc error
1 = Message was sent
If the user is not on a particular node it will also go into
limbo.
RetC = AdeptSysChatCustomMsg(line, PktType, To, Message)
0 - Syntax error
1 - Sent to server
AdeptSysChatCustomMsg allows you to send messages to the user that you
can parse via the rexx AdeptSysChatGetMsg. This allows you to add new
chat options, functions and types. You cannot specify a type below
1000, all types MUST begin with 1001 or higher, the bottom 1000 are
reseved for system use. You can have fun with this.
RetC = AdeptSysChatUserConnected(line)
Return Codes are:
0 - Syntax Error
1 - User connected
2 - User not connected
3 - Server down, obviosly the user is not connected.
Checks to make sure the user is properly connect to the chat server.
RetC = AdeptSysChatConnectUser(line)
Return Codes are:
0 - Syntax error
1 - User connected with server
2 - Failed to connect user to server
3 - Server unavailable
Will connect/sign up a user with the chat server.
RetC = AdeptSysCheckForServer(line)
Return Codes are:
0 - Syntax error
1 - Server not available
2 - Server available
Checks to make sure the chat server is available.
RetC = AdeptSysChatReconnectUser(line)
Return Codes are :
0 - Syntax error
1 - User connected to server
2 - Failed to reconnect user
3 - Sever not available
ChatReconnectUser should only be used to reconnect a user to the chat
server after it has gone down and the user was chatting in a conference.
RetC = AdeptSysChatMessageWaiting(line)
Return Codes are:
0 - Syntax Error
1 - There is a chat message waiting
2 - Error User Not Connected
3 - Error Server is Down
The BBS software makes calls to only one function to check to see
if a user has chat messages waiting.
If the file CHATREAD.CMD exists in the menus sub-directory for the
particular language the user has chosen it will execute that script
instead of the internal BBS function for displaying the message
to the user.
This allows you to customize the chat system from anywhere in the
BBS and not just make your own chat client/system.
The file chatread is not called if there are messages and your are
using the adeptchatinput function. It is called while you are
using any other adept input or system function.
**************************************************************************
External Editor Support Added:
The BBS Software will now look for the file EXTFSE#.CMD or EXTLE#.CMD
before loading the full screen or line message editor. If the file
exists it will execute it instead of the internal editors. If the
MSGTMP file in the users \Adept\System\Line# sub-directory doesn't
exist it considers the message as aborted, failed, etc.
YOU MUST HAS A SEPERATE .CMD FILE FOR EACH NODE.
The BBS will now execute (if exists) the .CMD file MSGTOUSERON.CMD
when a message is posted by anouther user on the BBS to anouther
user on the BBS. You can this use this command file to notify
the reciepient that they have new mail waiting. I also added
{DA Who the message was to
{DB The Message Subject
{DC Area name message was posted to
{DD Node number of receipient
{DE Area number the message was posted to
***************************************************************************
New Meta Added:
You must also add {PQ to the end of prompt #336 for it to work properly.
***************************************************************************
Drop File Added:
Added support for the dorinfo1.def drop file. It will put the file
dorinfo1.def into the System\line# sub-dir. This follows the base
dorinfo style format, no additional extentions.
***************************************************************************
New Text Files added :
The bbs will
now display the file ToLow.Asc (in the text dir) if it exists whenever a user
tries to access a menuitem that his security does not allow him to use. No more
users wondering why menu option don't work for them.
Have also added check for min/max age on menuitems and
will diplay ToYoung.Asc/ToOld.Asc respectivly if the user fails min or max age.
Will only display the files if they exist in the text dir, otherwise it's business
as usuual.
*****************************************************************************
Added LastMessage Read prompt:
Ok i was not real happy with my LMR prompt, so now it's an
entry in the language.text file it should look like this:
-----Snip-----
#908 LMR Update prompt
[ans]\rUpdate your LastRead Msg Pointers?[Y/n]
[asc]Update your LastRead Msg Pointers?[Y/n]
--------------
edit yur language.text to reflect this change and yur users will
have a prompt after download. Only if they have not chosen the
goodbye after download option. If they choose goodbye Lmr's
are updated before he is logged off.
*****************************************************************************
At long last adept will now respect events. It will check the users
remaining time allowed in the bbs for this logon, compare it to
the active events end time for this node (It is assumed that the next
event starts immediatly after the current one ends, valid assumption I think
since you should not have holes in yur event schedules anyway for proper
operation of the mailer) and if the users time is greater than time to next forced
event, his time will be adjusted accordingly. If an adjustment is made to
the users time he will be shown (if it exists in the text dir) the file
timeadjusted.asc/ans/avt/rip. You create this file and make it read
anything you like. Meta's are valid in this file just like all other
text files, so u can show the user his adjusted time if u like, or simply
inform him his time has been adjusted.. it's up to you.
I have included a timeadjusted.asc/ans file in this archive as a sample
of what u can do with it. Not fancy but it meets my needs for my bbs, do
with it what you will. =)
****************************************************************************
Ok, I have added the ability to use custom login.asc/ans files
on a per node basis, the bbs now looks for loginx.asc/ans where
x is the node number, so you can have a login1.asc/ans login2.asc/ans
etc..(Note if yur going to use this method, the .asc *MUST* exist or
the search will fail.) if it can't find a loginx.asc file, it will
default to the old behaviour of displaying the plain login.asc/ans.
This gives you great flexibilty and control over your login displays
for each node.
Of course I have also added the ability to display a custom
WelComex.Asc/Ans screen, again on a per node basis, if welcomex.asc
for that node doesn't exist, it will try to display welcome.asc/ans,
and if that doesn't exist it won't display a welcome message at all.
Note: these linex.asc/welcomex.asc files must be in the text dir
just the way the old files were in the text dir.
****************************************************************************
This build heralds Adepts coming into the color age, included
in this zip is a file called colors.ctl, simply place this file
in your \adept\system dir, edit the values to your liking, then
fire up adept. The screens will come up with fore/back ground
color combinations *YOU* selected. So if you like Lora's colors
fer instance you can set adept up to look like it. The screens
are all individually controlled as you can see in the colors.ctl
file, so be creative, choose color combos that look good to *YOU*.
NOTE: if the colors.ctl doesn't exist, Adept will still come up,
but it will come up with a set of default colors *I* picked.
If u wnat the old standard GRAY screens, simply set all background
to 204 and all foreground colors to 0, that'll give u black
text on gray background...
***************************************************************************
New feature, couple guys were asking bout the possibility of
of replying to echomail with a netmail, well it's done, and it
works. I've tested it here works like a champ. To enable this
little feature (yeah little after it works <G>) you need to edit
line #901 in your language.text file. Make it look like this:
#901 (Next Page, Prev Page, Over, Abort, Reply, Forward-thread, Backward-thread, Quit-thread, Kill, Move, Copy, Locate, LocateNext, LocatePrevious, #Msg, Description, rUles, =Again, Scan, Without stopping, !Toggle Ctrl-A, LocateUser)
[Str]NPOAR][.KMCL/\#DU=SW@! X*:
Note the added * character before the : it used to read X:
change it to X*: the * key will activate the reply as netmail
option when yu are reading any echomail message. Hell make that
*ANY* message, if you want to reply to a local base with netmail
well you can do so, didn't feel it was worth the added effort
to filter out the local bases. Note that all security options
and flags still apply here. If you don't have the flags or
security level to post in yur netmail area you won't be able to
enter the message. Oh and it doesn't matter what you call
your netmail area, i scan for the NETMAIL flag (you should
have it checked in your message areas setup already right?
Right!)
****************************************************************************
Reply to any message as E-Mail reply, this function now works, the tilde key invokes the
reply as e-mail option from the message reader menu. You
can reply to a message in *ANY* area as e-mail and not lose
your place in the area you are reading. Change line 901
of language.text so it looks like this now"
#901 (Next Page, Prev Page, Over, Abort, Reply, Forward-thread, Backward-thread, Quit-thread, Kill, Move, Copy, Locate, LocateNext, LocatePrevious, #Msg, Description, rUles, =Again, Scan, Without stopping, !Toggle Ctrl-A, LocateUser)
[Str]NPOAR][.KMCL/\#DU=SW@! X*~: <---- Note the tilde key right after
the *.
*****************************************************************************
Added 4 new menu commands, menu commands 119 and 120.
These work as the description for menu types 25 and 26.
Except, that these two will only act on *TAGGED* message
areas. The offline mail tags are what is inspected by them
when showing u the next area. So it is now possible for
your users to tag a bunch of msg areas, and using type
119 or 120 do a read of tagged areas. It tells the user
number of messages in the area, his last message read, then
the user has the option of reading the area, skipping it
setting direction etc.. just like types 25 and 26.
Menu Commands 121 and 122, these two will do a quick(121)
or detailed(122) scan of tagged message areas. Again the
user has the choice of doing the scan on the area presented
or skipping it. If he chooses R)ead he will read the message
headers. just like menu choices 16 and 17, but for all tagged
message areas instead of just the current area.
Give your users the option to tag message areas from yur
msgs menu by using either (or both) menu types 50 or 702.
The beauty of this scheme, is that the user can permanently
set tags that will be rememebred across logins, but at
any given login can (for that session only if he chooses) tag
a bunch of areas he doesn't want to be permanently tagged.
Unless the user saves his tags they will be lost at the next logon.
Note: If u have 5000 message areas and u tag area 1 and 5000,
and invoke one of these menu types, there's gonna be a noticeable
delay between the time u read the last message in area 1 and the
time area 5000 is presented to you for action. It takes *TIME*
to scan 5000 message areas looking for the area tagged bit.
****************************************************************************
Added a new command line switch, (Just for WIKK) if you
start adept with adept /nodes x /nostat it will fire
up *WITHOUT* the adept status screen, looking like pre 1.07
days before they added that status screen.
*****************************************************************************